perm filename LETTER.TXT[1,RWF]2 blob sn#826123 filedate 1986-10-10 generic text, type C, neo UTF8
COMMENT āŠ—   VALID 00003 PAGES
C REC  PAGE   DESCRIPTION
C00001 00001
C00002 00002
C00005 00003	\magnification =\magstephalf
C00007 ENDMK
CāŠ—;

A page width of 80 characters like this one requires large lateral eye motions,
and it is hard to find the right line at the end of the backscan.  I have been
told that it is good editorial practice to use no more than 70 characters per
line, and to me it seems about right.  Is there some way that most BBOARD
messages could be put into a narrower format?  For example, using a default line
width of 50 characters for EMAIL editing, or running most messages through a
reformatter when they are entered into BBOARDs.  The following paragraph is this
one in a narrower format.  This is 80 wide.

 
A page width of 80 characters like this one
requires large lateral eye motions, and it is hard
to find the right line at the end of the backscan.
I have been told that it is good editorial
practice to use no more than 70 characters per
line, and to me it seems about right.  Is there
some way that most BBOARD messages could be put
into a narrower format?  For example, using a
default line width of 50 characters for EMAIL
editing, or running most messages through a
reformatter when they are entered into BBOARDs.
The following paragraph is this one in a narrower
format.  This is 50 wide.

A page width of 80 characters like this
on requires large lateral eye motions,
and it is hard to find the right line at
the end of the backscan.  I have been
told that it is good editorial practice
to use no more than 70 characters per
line, and to me it seems about right.
Is there some way that most BBOARD
messages could be put into a narrower
format?  For example, using a default
line width of 50 characters for EMAIL
editing, or running most messages
through a reformatter when they are
entered into BBOARDs.  The following
paragraph is this one in a narrower
format.  This is 40 wide.
\magnification =\magstephalf

\input buslet
\def\disleft#1:#2:#3\par{\par\hangindent#1\noindent
			 \hbox to #1{#2 \hfill \hskip .1em}\ignorespaces#3\par}
\def\display#1:#2:#3\par{\par\hangindent #1 \noindent
			\hbox to #1{\hfill #2 \hskip .1em}\ignorespaces#3 \par}
\def\adx#1:#2\par{\par\halign{\hskip #1##\hfill\cr #2}\par}


\rwflet

\vskip 30pt
	
\address 
Mr.~Greg Chaitin
IBM Corporation
T.~J.~Watson Research Center
P.~O.~Box 218
Yorktown Heights, NY 10598

\body
Dear Greg:

I am sending separately a copy of Paul Hallowell's master's thesis,
``Top-Down Passing Syntax Error Recovery,'' which I mentioned on the
phone. He implemented and tested my method for top-down analysis with
largely automatic error recovery and diagnosis. Please pass it on to
the right people.

\closing
Sincerely yours,
Robert W.~Floyd 

\annotations
RWF/rfn
%\smallskip
%Enclosure
%\smallskip
%cc: Matthew Kahn
%\smallskip
%\ps
%P.S.: whatever you wish to say here

\endletter

\makelabel
\end